feat: API regeneration: release-2025-12-08.09-02-28 #3086
Conversation
Summary of ChangesHello @amanda-tarafa, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request encompasses a broad regeneration of API definitions across numerous Google Cloud services. The primary goal is to synchronize the client libraries with the latest API schemas, introducing new features, refining existing functionalities, and enhancing documentation for improved developer experience and clarity. Key updates range from new data structures and methods to minor descriptive corrections and strategic deprecations, ensuring the libraries remain current and robust. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
Summary of ChangesHello @amanda-tarafa, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on updating and regenerating various Google API schemas. These changes introduce new features, correct existing descriptions, and update revisions to reflect the latest API definitions. The updates span multiple services, including Access Approval, Ad Exchange Buyer II, Admin Reports, Android Publisher, Backup DR, BigQuery Reservation, Calendar, Classroom, Cloud Build, Cloud Channel, Cloud Shell, Cloud Support, Contact Center AI Platform, Container, Data Catalog, Dataform, Data Fusion, Datamigration, Dataplex, Datastream, Deployment Manager, Developer Connect, Docs, Document AI, DoubleClick Bid Manager, Drive, Eventarc, Firebase App Distribution, FirebaseML, GKE Hub, Gmail, Healthcare, IDS, Logging, NetApp, Network Connectivity, Notebooks, OS Login, Policy Simulator, Recaptcha Enterprise, Run, Search Ads 360, Security Center, SQL Admin, Storage, Tag Manager, Text-to-Speech, and TPU. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a series of automated changes for API regeneration. The updates span multiple API discovery files and their corresponding C# client libraries, including revision number increments, addition of new features, enums, and endpoints, as well as description corrections. The changes are largely consistent with an automated process. I've identified and suggested a fix for a minor typo in the description of a new field within the cloudsupport API discovery files.
| "type": "string" | ||
| }, | ||
| "downloadExternalReadToken": { | ||
| "description": "# gdata.* are outside protos with mising documentation", |
There was a problem hiding this comment.
There is a typo in the description. 'mising' should be 'missing'.
| "description": "# gdata.* are outside protos with mising documentation", | |
| "description": "# gdata.* are outside protos with missing documentation", |
| "type": "string" | ||
| }, | ||
| "downloadExternalReadToken": { | ||
| "description": "# gdata.* are outside protos with mising documentation", |
There was a problem hiding this comment.
There is a typo in the description. 'mising' should be 'missing'.
| "description": "# gdata.* are outside protos with mising documentation", | |
| "description": "# gdata.* are outside protos with missing documentation", |
2 participants
Changes in this PR will be published to Nuget on the next release cycle.